From 4d670fceb13f1580b759f381a522e5624ee30b0c Mon Sep 17 00:00:00 2001 From: robertl Date: Mon, 14 Mar 2005 18:14:41 +0000 Subject: [PATCH] Reorder so that (eternally growing) list of file notes comes after usage. --- gpsbabel/README | 132 ++++++++++++++++++++++++------------------------ 1 file changed, 66 insertions(+), 66 deletions(-) diff --git a/gpsbabel/README b/gpsbabel/README index 831a5ac6b..aa96cde91 100644 --- a/gpsbabel/README +++ b/gpsbabel/README @@ -37,6 +37,72 @@ GETTING IT / BUILDING IT Exapt can be downloaded from http://expat.sourceforge.net and is part of Apache so it's very portable. +COMMON USAGE + + Invocation was meant to be flexible. Unfortunately, that can + sometimes lead to unwieldy command lines. + + gpsbabel -? + + will always show you the supported file types. To use this + program, just tell it what you're reading, where to read it from, + what you're writing, and what to write it to. For example: + + gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx + + tells it to read the first file in geocaching.com format and create + a new file in GPX format. + + This command will read from a Magellan unit attached to the first + serial port on a Linux system (device names will vary on other OSes) + and write them as a geocaching loc file. The second command does + the same for windows. + + gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc + gpsbabel -i magellan -f com1 -o geo -F mag.loc + + + Optionally, you may specify "-s" in any command line. This causes + the program to ignore any "short" names that may be present in the + source data format and synthesize one from the long name. This + is particularly useful if you're writing to a target format that + isn't the lowest common denominator but the source data was written + for the lowest common denominator. I use this for writing data + from geocaching.com to my Magellan so my waypoints have "real" names + instead of the 'GC1234' ones that are optimized for NMEA-only + receivers. A geocacher with a Magellan receiver may thus find + commands like this useful. + + gpsbabel -s -i geo -f geocaching.loc -o magellan -F /dev/ttyS0 + gpsbabel -s -i geo -f geocaching.loc -o magellan -F com1 + +ADVANCED USAGE + + Argument are processed in the order they appear on the command line. + Input is cumulative. The input file type remains unchanged until a + new -i argument is seen. Files are read in the order they appear. + So you could merge three input files into one output file with: + + gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc + + You can merge files of different types: + + gpsbabel -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx -o gpsutil -F big.gps + + You can write the same data in different output formats: + + gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx 1.wpt + +ROUTE AND TRACK MODES + + The presence of "-t" on the command line tells us to work with + tracks. The presence of "-r" tells us to work with routes. + Tracks and routes are advanced features and don't try to + handle every possible hazard that can be encountered during a + conversion. If you're merging or converting files of similar + limitations, things work very well. The presence of "-s" on + the command line tends to creat havoc because tracks and routes. + THE FORMATS GPX @@ -962,69 +1028,3 @@ DATA FILTERS -x stack,pop,append \ -o magellan -F fwaind.wpt -COMMON USAGE - - Invocation was meant to be flexible. Unfortunately, that can - sometimes lead to unwieldy command lines. - - gpsbabel -? - - will always show you the supported file types. To use this - program, just tell it what you're reading, where to read it from, - what you're writing, and what to write it to. For example: - - gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx - - tells it to read the first file in geocaching.com format and create - a new file in GPX format. - - This command will read from a Magellan unit attached to the first - serial port on a Linux system (device names will vary on other OSes) - and write them as a geocaching loc file. The second command does - the same for windows. - - gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc - gpsbabel -i magellan -f com1 -o geo -F mag.loc - - - Optionally, you may specify "-s" in any command line. This causes - the program to ignore any "short" names that may be present in the - source data format and synthesize one from the long name. This - is particularly useful if you're writing to a target format that - isn't the lowest common denominator but the source data was written - for the lowest common denominator. I use this for writing data - from geocaching.com to my Magellan so my waypoints have "real" names - instead of the 'GC1234' ones that are optimized for NMEA-only - receivers. A geocacher with a Magellan receiver may thus find - commands like this useful. - - gpsbabel -s -i geo -f geocaching.loc -o magellan -F /dev/ttyS0 - gpsbabel -s -i geo -f geocaching.loc -o magellan -F com1 - -ADVANCED USAGE - - Argument are processed in the order they appear on the command line. - Input is cumulative. The input file type remains unchanged until a - new -i argument is seen. Files are read in the order they appear. - So you could merge three input files into one output file with: - - gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc - - You can merge files of different types: - - gpsbabel -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx -o gpsutil -F big.gps - - You can write the same data in different output formats: - - gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx 1.wpt - -ROUTE AND TRACK MODES - - The presence of "-t" on the command line tells us to work with - tracks. The presence of "-r" tells us to work with routes. - Tracks and routes are advanced features and don't try to - handle every possible hazard that can be encountered during a - conversion. If you're merging or converting files of similar - limitations, things work very well. The presence of "-s" on - the command line tends to creat havoc because tracks and routes. - -- 2.30.2